…pport

workerd's Windows SQLite code path in sqlite.c++:511 uses
kj::Path::toString() which produces Unix-style forward-slash paths
(e.g. D:/a/_temp/...), but passes nullptr VFS to sqlite3_open_v2()
which uses the win32 VFS expecting native paths. This causes
SQLITE_CANTOPEN. The fix is in workerd (toString -> toNativeString),
skip the test until then.

…pport

# Conflicts:
#	pnpm-lock.yaml

Ephemeral DOs don't support getByName() which the pool needs to
connect to the runner singleton via getDurableObjectNamespace().
The runner DO uses KV-backed storage (not SQLite) so it isn't
affected by the Windows SQLite path bug anyway.

workerd's Windows SQLite VFS uses kj::Path::toString() which produces
Unix-style forward-slash paths, causing SQLITE_CANTOPEN with the win32
VFS (cloudflare/workerd#6110). Instead of excluding SQLite DO fixtures
on Windows, use unsafeEphemeralDurableObjects to switch all DOs to
in-memory storage. This avoids disk SQLite paths entirely while keeping
DOs fully functional (including SQLite-backed ones). Cross-restart
persistence isn't needed for tests.

unsafeEphemeralDurableObjects doesn't work: inMemory storage doesn't
support enableSql (SQLite-backed DOs) and listDurableObjectIds reads
from disk. There's no miniflare-level workaround for the workerd
Windows SQLite path bug — disk-backed SQLite DOs require localDisk
storage. Re-add the durable-objects fixture exclusion on Windows
until workerd#6110 ships.

…dead code

- Remove duplicate tailStream in WORKER_ENTRYPOINT_KEYS
- Fix cycle detection in getCjsNamedExports (seen.add wrong variable)
- Fix isEnabled() to match assertIsEnabled() semantics (disable flag precedence)
- Fix missing space in user-facing error message
- Fix SELF proxy crash on non-function properties
- Fix structuredSerializableStringify mutating caller's object
- Improve connectToMiniflareSocket error on WebSocket failure
- Add no-op methods to BroadcastChannel stub
- Fix off() to map Vitest event names to WebSocket events
- Fix garbled getSerializedOptions error message
- Remove TODO(now), commented-out code, stale comments
- Remove redundant ?? true after Zod default
- Add cross-referencing comments for shared magic strings

…nding (#7717)

generateAssetsFetch() in wrangler creates a chokidar watcher for _headers
and _redirects files that was never closed. This kept the Node.js event loop
alive, causing Vitest's "close timed out" warning on every test run.

Wire an AbortSignal through generateAssetsFetch() so the watcher can be
closed on demand. In vitest-pool-workers, track AbortControllers in a
module-level registry and abort them all in CloudflarePoolWorker.stop().

…ion and large provide data

- bare-specifiers.test.ts: import "url", "path", "buffer" without node: prefix (#6214)
- large-provide.test.ts: 50 KB provide/inject payload that exceeded v3 header limit (#9957)

- Reference-count active workers so watchers only close when the last
  worker stops, not when the first one does
- Move AbortController registration after the wrangler import so a
  failed import does not leak an orphaned controller
- Handle already-aborted signals in generateAssetsFetch
- Catch errors from watcher.close() to avoid unhandled rejections

…pport

# Conflicts:
#	pnpm-lock.yaml

…pport

# Conflicts:
#	pnpm-lock.yaml

…flags

Replace hand-written polyfills with workerd's native implementations:
- node:v8 stub → nodejs_v8_module compat flag
- process.memoryUsage/EventEmitter prototype → nodejs_process_v2 compat flag
- globalThis.Buffer → already provided by nodejs_compat_v2
- globalThis.process, process.argv, process.versions.node → already provided by nodejs_compat_v2/process_v2

Fix unhandled rejection in runDurableObjectAlarm (return → return await)
to prevent intermediate rejected promise with process_v2's proper
unhandledrejection tracking.

Fix request-mocking fixture: replace HttpResponse.error() with HTTP 400
to avoid MSW-internal TypeError escaping as unhandled rejection.

…dlers

Add `await` to `return` statements in handleRequest() that call async
sub-handlers (handleTokenExchange, updatePreviewToken, handleRawHttp).

Without `await`, when these functions throw synchronously (e.g. via
assertValidURL), the intermediate rejected promise is reported as an
unhandled rejection before the outer try/catch can handle it. This is
a workerd process_v2 behaviour difference vs Node.js — to be reported
upstream.